Skip to content

Conversation

@taylorwilsdon
Copy link
Contributor

@taylorwilsdon taylorwilsdon commented Jun 2, 2025

This pull request updates the MCP documentation to reflect the introduction of Streamable HTTP as the modern standard for remote server transport while retaining docs for the existing SSE transport as legacy.

This ensures our documentation is current with the latest MCP SDK capabilities and guides users towards best practices for new server implementations.

Key changes include:

  • docs/features/mcp/server-transports.md:
    • Updated title and introduction to include Streamable HTTP and mark SSE as legacy.
    • Added a new comprehensive section detailing "Streamable HTTP Transport," including:
      • How it works, with a diagram.
      • Its characteristics and ideal use cases.
      • An example configuration.
      • Information on backwards compatibility with the older HTTP+SSE transport.
    • Updated the "Hosted Deployment Model" subsection to "Streamable HTTP / SSE (Legacy): Hosted Deployment Model."
    • Revised the comparison table in "Choosing Between Transports" to include Streamable HTTP and reflect SSE's legacy status.
    • Updated the link in "Configuring Transports in Roo Code" to reflect all three transport types.
  • docs/features/mcp/using-mcp-in-roo.mdx:
    • Updated the "Understanding Transport Types" introduction to mention three transport types (STDIO, Streamable HTTP, and SSE Legacy).
    • Inserted a new "Streamable HTTP Transport" subsection with:
      • A description highlighting it as the modern standard.
      • Key characteristics.
      • A link to the detailed section in server-transports.md.
      • Configuration parameters and an example.
    • Modified the "SSE Transport" subsection to "SSE Transport (Legacy)," advising Streamable HTTP for new servers, and updated its description and configuration example to reflect its legacy status and the importance of the type parameter.
  • docs/advanced-usage/available-tools/use-mcp-tool.md:
    • Updated "Key Features" to include StreamableHTTPClientTransport.
    • Added StreamableHTTPClientTransport to the list of transport mechanisms in the "Tool Invocation Process" section.
  • docs/features/mcp/overview.md:
    • Updated the link description for "Server Transports" to include Streamable HTTP.
  • docs/features/mcp/what-is-mcp.md:
    • Updated the link description for "Server Transports" to include Streamable HTTP.

These changes provide users with clear and up-to-date information on MCP server transport options, promoting the use of Streamable HTTP for new developments.

Will follow up with a second pass more content focused, just wanted to get this in for now to match up with the merge of RooCodeInc/Roo-Code#4210

@mrubens - this should cover at least the merged change, thanks!


Important

Updates MCP documentation to introduce Streamable HTTP as the modern standard for server transport, marking SSE as legacy, with detailed changes across multiple files.

  • Behavior:
    • Updates server-transports.md to introduce Streamable HTTP as the modern standard for MCP server transport, marking SSE as legacy.
    • Adds detailed section on Streamable HTTP, including its workings, characteristics, use cases, and example configuration.
    • Revises comparison table to include Streamable HTTP and reflect SSE's legacy status.
  • Documentation:
    • Updates using-mcp-in-roo.mdx to include Streamable HTTP in transport types and configuration examples.
    • Modifies overview.md and what-is-mcp.md to update links and descriptions to include Streamable HTTP.
    • Updates use-mcp-tool.md to list StreamableHTTPClientTransport as a supported transport mechanism.
  • Misc:
    • Updates various sections to advise using Streamable HTTP for new server implementations and maintain compatibility with older SSE transport.

This description was created by Ellipsis for 01fb129. You can customize this summary. It will automatically update as commits are pushed.

@vercel
Copy link

vercel bot commented Jun 2, 2025

@taylorwilsdon is attempting to deploy a commit to the Roo Code Team on Vercel.

A member of the Team first needs to authorize it.

@hannesrudolph hannesrudolph merged commit 20b7b7c into RooCodeInc:main Jun 2, 2025
1 of 2 checks passed
@github-project-automation github-project-automation bot moved this from Triage to Done in Roo Code Roadmap Jun 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants